Repository navigation
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.
|
The README branch is current with master and conflict-free, but its head has no check runs, commit statuses, or workflow runs, so the requested green-CI merge condition is not met. @yegor256, CI availability is the blocker; draft workflow PR #9 remains with its Maven CI owner. A successor wish will finish #10 once head CI is green. |
The file-age example supplies three operands to binary
plusand testsnow + 5h30m > utime, which classifies nearly every file as too old. Nest two binary additions and comparenow > utime + 5h30m. The explanation now states that exactly 5h30m counts as fresh.Closes #7. Only README.md changes; the nanosecond example in #6 remains separate.
Validation: an external indentation-based check reproduced the three-operand failure before the change, then verified binary arity and fresh, exactly 5h30m-old, older, and future timestamp cases after it.
git diff --checkpasses. Master contains only README.md, with no Maven project or workflow runs, so no EO runtime or full-build claim is made. Global local pre-commit checks report pre-existing README formatting and missing REUSE metadata; these remain visible and unchanged. Submitted through GitHub's commit API without changing hook configuration.Subsequent PR/CI work remains with the existing eo-time maintenance wishes. Sync with master and gh-merge a green, conflict-free head immediately without reviews; never Rultor.